home *** CD-ROM | disk | FTP | other *** search
/ NetNews Offline 2 / NetNews Offline Volume 2.iso / news / comp / lang / c++-part1 / 5596 < prev    next >
Encoding:
Internet Message Format  |  1996-08-05  |  986 b 
  1. Path: nnrp.info.ucla.edu!geoff
  2. From: geoff@ficus.cs.ucla.edu (Geoff Kuenning)
  3. Newsgroups: comp.lang.c++
  4. Subject: Re: Derived classes inter-referencing each other
  5. Date: 5 Feb 1996 21:29:22 GMT
  6. Organization: Ficus Research Project, UCLA Computer Science Department
  7. Message-ID: <4f5sri$1g0s@saba.info.ucla.edu>
  8. References: <4em3ta$2p0@delphi.cs.ucla.edu> <4f0n91$a3b@news2.ios.com>
  9. NNTP-Posting-Host: exeter.cs.ucla.edu
  10.  
  11. In article <4f0n91$a3b@news2.ios.com> vlad@gramercy.ios.com (Vlastimil
  12. Adamovsky) writes:
  13.  
  14. > Unless there is some special reason behind your code, you could use a
  15. > pointer instead a reference. Then, it shoud work with a forward
  16. > declarations.
  17.  
  18. Seems unlikely.  The problem isn't lack of knowledge of structure
  19. layout (a reference is equivalent to a pointer for that difficulty).
  20. The problem is that the compiler needs to know that "bar" is derived
  21. from "barbase".
  22. -- 
  23.     Geoff Kuenning    g.kuenning@ieee.org    geoff@ITcorp.com
  24.     http://www.cs.ucla.edu/ficus-members/geoff/
  25.